-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RDoc-3179 Update the Cluster Configuration #1979
RDoc-3179 Update the Cluster Configuration #1979
Conversation
|
||
{NOTE: } | ||
|
||
* The primary goal of the `Cluster Observer` is to maintain the [Replication Factor](../../../server/clustering/distribution/distributed-database#replication-factor) of each database in the cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The primary goal is to monitor the health of each database and adjust the topology accordingly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Let's assume it is distributed to B, C and E (so the database group is [B,C,E]), | ||
and the cluster decides that node C is responsible for performing the ETL task. | ||
|
||
* If node C goes offline or is not reachable, the Observer will notice it and relocate the database from node C to another available node. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
relocate the database
This is last resort and not something we do frequently... since it is a heavy operation. consider a large database with many indexes. to replicate it and to index everything on a new node might take some time and resources.
first we will rotate the topology or move this node to rehab and due to the topology change a different node will be selected to do the task.
if that node is offline for a long period of time we start the relocation (need to check which config define this time)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Related issue:
https://issues.hibernatingrhinos.com/issue/RDoc-3179/Update-the-Cluster-Configuration
Updated the configuration article:
Documentation/6.2/Raven.Documentation.Pages/server/configuration/cluster-configuration.markdown
Updated only the values mentioned in:
Documentation/6.2/Raven.Documentation.Pages/server/clustering/distribution/cluster-observer.markdown